Skip to content

Remove bors and use GitHub merge queue#913

Merged
brunoocasali merged 1 commit into
mainfrom
remove-bors
Dec 1, 2025
Merged

Remove bors and use GitHub merge queue#913
brunoocasali merged 1 commit into
mainfrom
remove-bors

Conversation

@curquiza
Copy link
Copy Markdown
Member

@curquiza curquiza commented Dec 1, 2025 •
edited
Loading

Ruleset set up for the usage of GitHub merge queue ✅

Summary by CodeRabbit

  • Chores
    • Simplified CI/CD workflow triggers and event handling.
    • Updated contribution guidelines to streamline the PR submission process by removing branch synchronization requirements.
    • Removed references to legacy automation tools from documentation and release workflows.
    • Fixed minor formatting inconsistencies in documentation.

✏️ Tip: You can customize this high-level summary in your review settings.

@curquiza curquiza added the maintenance Anything related to maintenance (CI, tests, refactoring...) label Dec 1, 2025
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Dec 1, 2025 •
edited
Loading

Walkthrough

These changes remove references to and automation for the bors bot across configuration and documentation, modify CI/CD workflow triggers to include merge_group events while narrowing push triggers to main, and fix minor documentation formatting.

Changes

Cohort / File(s) Summary
Bors/automation removal
\\.github/release-draft-template.yml, CONTRIBUTING.md		 Removed @bors and @meili-bors bot mention replacements from release template; removed outdated contributor guidance on PR rebasing, bot-based automation sections, and bors documentation references.
Workflow trigger updates
\\.github/workflows/tests.yml		 Modified push trigger to target only main branch (removed trying/staging); added merge_group trigger alongside pull_request.
Documentation fixes
README.md		 Removed trailing whitespace in JSON snippet (minor formatting).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Verify that removing @bors and @meili-bors replacements doesn't break downstream workflows or release processes
  • Confirm that the merge_group trigger aligns with the project's merge strategy and GitHub Actions configuration
  • Ensure that the removed bors automation guidance in CONTRIBUTING.md reflects the actual deprecation of bot-based tooling

Poem

🐰 The bots have retired, their tasks now complete,
Merge groups arrive for automation sweet,
Docs cleaned and tidied, the workflow runs bright,
With workflows refined, the CI/CD takes flight! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title directly reflects the main objective of the PR: removing bors bot integration and transitioning to GitHub's merge queue feature.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch remove-bors
📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 1ae39ac and d8d5d92.

📒 Files selected for processing (4)
  • .github/release-draft-template.yml (0 hunks)
  • .github/workflows/tests.yml (1 hunks)
  • CONTRIBUTING.md (0 hunks)
  • README.md (1 hunks)
💤 Files with no reviewable changes (2)
  • .github/release-draft-template.yml
  • CONTRIBUTING.md
🔇 Additional comments (2)
README.md (1)

240-240: Minor whitespace cleanup in JSON example.

Removing trailing whitespace in the JSON output example is a good housekeeping change with no impact on documentation.

.github/workflows/tests.yml (1)

6-8: Workflow triggers correctly configured for GitHub merge queue.

The changes appropriately transition from bors automation to GitHub's native merge queue:

  • Narrowing push triggers to main aligns with merge queue semantics (no more try/staging branches).
  • Adding the merge_group event enables workflows to execute when PRs are queued in the merge queue.

The existing job condition remains valid and will continue filtering pre-release PRs correctly.

Comment @coderabbitai help to get the list of available commands and usage tips.

@curquiza curquiza requested a review from brunoocasali December 1, 2025 16:31
@brunoocasali brunoocasali added this pull request to the merge queue Dec 1, 2025
Merged via the queue into main with commit 2cae26d Dec 1, 2025
3 checks passed
@brunoocasali brunoocasali deleted the remove-bors branch December 1, 2025 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@brunoocasali brunoocasali brunoocasali approved these changes

Assignees

No one assigned

Labels

maintenance Anything related to maintenance (CI, tests, refactoring...)

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@curquiza @brunoocasali